Skip to content

Automate @hypervideo/drizzle-orm publishes from main#2

Closed
danieljvdm wants to merge 1 commit intomainfrom
dan/hyper-main-publish
Closed

Automate @hypervideo/drizzle-orm publishes from main#2
danieljvdm wants to merge 1 commit intomainfrom
dan/hyper-main-publish

Conversation

@danieljvdm
Copy link
Copy Markdown

Summary

  • add a GitHub Actions workflow that publishes @hypervideo/drizzle-orm on pushes to main and via manual dispatch
  • compute the next -hyper.N version for whatever base version drizzle-orm/package.json currently declares on main
  • rewrite the packed tarball metadata so the published package is scoped to @hypervideo, points at hypervideo/drizzle-orm, and publishes to GitHub Packages

Notes

  • this automates the main release line exactly as requested
  • hypervideo/main currently has drizzle-orm@0.45.1, so the first automated main release would be 0.45.1-hyper.0
  • the beta/effect fork release we published today (1.0.0-beta.17-hyper.1) was published manually from the separate beta-based branch
  • the workflow prefers secrets.NPM_TOKEN when present and falls back to GITHUB_TOKEN

Validation

  • verified the tarball rewrite helper locally against a packed @hypervideo/drizzle-orm artifact
  • YAML parse check passed for .github/workflows/publish-hyper-drizzle-orm.yaml

@danieljvdm
Copy link
Copy Markdown
Author

Superseded by #3. We only want automated publishes from beta; main should never publish.

@danieljvdm danieljvdm closed this Mar 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant